Hackers Underworld 2: Forbidden Knowledge/Hackers Underworld 2: Forbidden Knowledge.iso/HACKING/HP3000_T.TXT

Text File | 1994-07-17 | 15KB | 359 lines

 _____________________________________________________________________________
|                                                                             |
|                            +==================+                             |
|       On Broadway          |HACKING THE HP3000|       Castle Brass          |
|     (415) xxx-xxxx         +==================+      (415) xxx-xxxx         |
|                                                                             |
|       -=Agents=-              Written by...             -=The=-             |
|         -=of=-                                         -=Castle=-           |
|       -=Fortune=-               ________\/             -=Knights=-          |
|                                / DE BUG 00                                  |
|   Seven Gates of Hell          \_\_\_\_\_>            Speed Demon           |
|     (415) xxx-xxxx             / \ / \ / \           (415) xxx-xxxx         |
|                                                                             |
|_____________________________________________________________________________|


PREFACE
#######

This instruction tutorial was written to help members of the hacking community
by giving them useful information about HEWLETT-PACKARD's HP3000 series of
mainframe computers.

The following abbreviations will be used throughout the entirety of this file:

<CR>              -   CARRIAGE RETURN, RETURN, ENTER, ETC.
^Y                -   CONROL CHARACTER (CONTROL-Y IN EXAMPLE)
CAPITAL LETTERS   -   COMPUTER OUTPUT AND USER INPUT

SYSTEM INFORMATION
###### ###########

Unlike its predecessor, the HP2000, the HP3000 runs on the MPE V operating
system which can support up to 101 LDEVs (Logical Devices) in a time-sharing
environment.  MPE V allows the 3000 to access many more software/database
packages than the 2000, as it is =not= a TSB (Time Shared Basic Environment).
The systems usually run on various levels of MPE V, although I have heard
that Hewlett-Packard is now beginning to upgrade the CPU and systems design
of their machine in order for a better chance at competing with other large
mainframe computers (The 3000 was put together in 1979!)


LOGON PROCEDURE
##### #########

HP3000s are distinguishable from other systems merely by their initial
logon message which you get after a couple of <CR>'s, ^F's, or ^E's:

:EXPECTED :HELLO, :JOB, :DATA  (CIERR 1402)

MPE is easily recognized by its : prompt.  Once you have received the :
prompt, you are then allowed a chance at logging on. The logon process
will contain the following pieces of data:

JOB ID       :  This is used to allow users to distinguish terminal sessions
                that are being run on the same group name. It consists of 1
                letter followed by up to 7 characters (not ','). My favorite
                ones to use are MANAGER, OPERATOR, and some nasty ones when
                I get frustrated or bored. The first time hacker may not wish
                to use these as they draw unwanted attention if they are not
                used in the right ways.

USER NAME    :  The user name consists of up to 8 letters, (e.g.) GEBHARDT

GROUP NAME   :  The group name consists of up to 8 letters and is often times
                the same as the account name, but not always! (We'll discuss
                determination of all of these later..)

ACCOUNT NAME :  The account name consists of 1 letter followed by up to
                7 letters or digits (I may have seen more, but usually these
                account names are kept as short as possible...)

PASSWORD     :  The passwords are from 1 to 8 printing and/or non-printing
                (CONTROL) characters. As with the 2000, the following
                characters will never be found in any PW's so don't bother:
                LINE DELETE (^X), NULL (^@), RETURN (^M), LINEFEED (^J),
                X-OFF (^S), X-ON (^Q), UNDERSCORE (_)


LOGON FORMAT
##### ######

:HELLO (JOB ID),(USER NAME)/(USER PW).(ACCOUNT NAME),(GROUP NAME)/(GROUP PW)

The passwords may not be typed in at the same time as the user/group/acct
names, as the 3000 will prompt for them afterwards, but that is up to your
discretion. A simpler example would be:

HELLO MANAGER.SYS,PUB (Remember, the JOB ID is not needed! Optional!)

The computer will then respond with...

ENTER USER PASSWORD:

..if the user/group/account all exist. Once past this one, you might
have to hack a group pw as well (usually not...)

LOGON NOTE:  User and Group PW's are =NOT= necessary! If you get lucky,
             the sysop might not have implemented one onto the them!
             If this is the case, you will be automatically logged on!

A final comment on the logon sequence: The only USER NAMES/GROUP NAMES
that are =always= going to be found on the 3000 are:

MANAGER.SYS,PUB (or maybe just plain MANAGER.SYS)
FIELD.SUPPORT

If you hack these, then you have PRIVs and will be able to make your own
accounts and/or use others. So, you the hacker, will try:

:HELLO MANAGER.SYS,PUB (if it works, then good!)
:HELLO MANAGER.SYS
:HELLO FIELD.SUPPORT

The HP3000 system is usually set to allow you one try at hacking a certain
user-account, and you will have three tries at the PW before it cans you.
Hewlett-Packard has stepped up its security from the 2000!


USERS
#####

The various users are identified by their USER ID (GEBHARDT), their group
name (GEBHARDT), their ACCOUNT NAME (SBA), and their PASSWORD. USER ID's
have an allocated CPU time, connect time, and user privileges ranging from
SYSTEM MANAGER capability down to just being able to run BASIC or PASCAL.
GROUP ID's are allocated file space on the disks, and are able to support
many #'s of USER ID's on them (e.g.) 5 USERS with USER ID's of:

NELSON, GEBHARDT, SEKHON, DEGNAN, and JEBIAN are all attached to the same
GROUP NAME of CSCI. Each of them is able to have different CPU allocations
and logon time, but all of their files are stored in the same group (CSCI)
and they share the same file directory. Thus, say user JEBIAN wants to
logon. Let's say his ACCOUNT NAME is ADVANCED. His logon process would be:

:HELLO JEBIAN.ADVANCED,CSCI

..and then he would enter his PASSWORD(s)...

The 3000 has ACCOUNT MANAGERS for each of its accounts (there may be up to
24 different ACCOUNT NAMES, each supporting up to 150 or so GROUPS, which
in turn can support 12 USER NAMES...) Unlike the 2000, there may be more than
one MANAGER for every account, all with the same powers. ACCOUNT MANAGERS
do not have full system privs like the MANAGER.SYS does, but they may still
create their own USER and GROUP names, so if you hacked one of these, then
you essentially control an account and may make your own user accounts for
future use or trading. The 3000 may also have other system managers besides
the MANAGER.SYS, so once you have hacked his PW, you can create other
system manager accounts, and even make non-privileged accounts have privs!
(We will discuss this later...)


NON-PRIVILEGED COMMANDS
### ########## ########

SHOWJOB - Lists =ALL= users and their respective acct/group info as well
          as their session # and their message reception status. If the
          word QUIET is printed, then that particular session will not
          receive messages from you.

SHOWME  - Lists everything you might want to know about your current job
          session. (i.e.) job #, LDEV #, time on, your USER/GROUP/ACCOUNT
          ID's, and more...

SHOWTIME - Lists the time and date.

REPORT  - Lists allocated disk space for the group, as well as total disk
          volume for the ACCOUNT ID. Also shows allocated CPU and total
          used CPU seconds. System manager may do a REPORT @.(ACCT NAME)
          which will tell info on the specified account.

LISTF @.(GROUP NAME).(ACCOUNT NAME)

This command (LIST FILES) allows the user the list the files in any group
directory in any account. Say you wanted to see the files in GEBHARDT.HS,
you would do this: